View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000884 | T99X171.00 SKB Eagle | SW Issue | public | 2020-08-14 19:53 | 2020-09-14 21:28 |
| Reporter | (ALTech) SY Yoon | Assigned To | (ALTech) SY Yoon | Due Date | 2020-08-19 20:44 |
| Priority | high | Severity | s2-severe | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Summary | 0000884: [Eagle][ATT] VoD test doesn't work sometimes in latest SW. | ||||
| Description | Dear Mr. Bcan Yeh, We are testing ATT with SW version ATV v. 15.520.8 AOSP v. 17.520.6 ATT Deamon version. 191105 We have issue with VoD test. My understanding of VoD Test is STB shows Search window “JAM” character is inputted in search window Select VoD contents and play It doesn’t show Search window sometimes. In this condition, I try to press Seach button(RCU BT10 for AOSP STB has search button), then STB shows search window. I captured log both cases. Could you check why search window isn't shown sometimes ? main_log_OK.log : It is the case that STB shows search window. It is log when input search event. 08-14 20:00:03.747 6463 6463 I Input : injectKeyEvent: KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_SEARCH main_log_NOK.log : It is the case that STB doen't show search window. It is log when input search event. 08-14 20:30:50.770 6402 6402 I Input : injectKeyEvent: KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_SEARCH I tested with STBCommunicationTester. New Firmware add another RCU(BA02 and BT11), but I tested it BA01 and BT10. | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
| User List |
|
|---|
|
|
|
|
|
The new SW was passed SKB BMT. So we need to find solution to change ATT deamon, not STB firmware. |
|
|
Hi Mr. Yoon, According to the log files you provided, main_log_OK.log: At line 18620, you can check the argument shows 'REBOOT_STEP=2'. Please refer to page 7 of 'STB ATT SystemInterconnectProtocol_v7.2-2'. AttDaemon run the step 2 of the aging test. main_log_NOK.log At line 18262, you can check the argument shows 'REBOOT_STEP=3'. Please refer to page 8 of 'STB ATT SystemInterconnectProtocol_v7.2-2'. AttDaemon run the step 3 of the aging test. Step 2 will do VOD test and Step 3 will finish the aging test. Please check it. |
|
|
Hi Becan Yeh, I attached log files. I used ATT tool. Both attached file has REBOOT_STEP=2, but one is OK and the other is not OK. Could you check it again ? |
|
|
Hi Mr.Yoon, main_log_NOK-2.log seems not complete. Below is the received command. -------------------------------------------------------- MSG-KIND:COMMAND COMMAND-KIND:VOD DATA-LENGTH:126 1C,5000 2B,3000 25,3000 22,3000 26,3000 <-------- the log terminate after sending key 26 0F,3000 12,3000 10,3000 12,3000 12,3000 11,3000 12,3000 11,3000 12,3000 -------------------------------------------------------- The log terminate after sending key 26. You can check it at line 53905 of main_log_NOK-2.log. The time of line 53905 is 08-18 19:31:15.550. The time of the last line is 08-18 19:31:17.655. I think that you may miss some log. Please provide a complete log for not OK case. |
|
|
Hi. Bcan Yeh, I have question. 1. main_log_NOK-2.log 08-18 19:30:58.365 4171 4171 D mUHDSTBGlobalkeyBroadCastReceiver: onReceive() keyCode : 84, action : KeyEvent.ACTION_UP 08-18 19:30:58.368 4171 4171 D mUHDSTBGlobalkeyBroadCastReceiver: onReceive() keyCode : 84, action : KeyEvent.ACTION_UP 2. main_log_OK-2.log 08-18 18:49:10.315 4206 4206 D mUHDSTBGlobalkeyBroadCastReceiver: onReceive() keyCode : 84, action : KeyEvent.ACTION_DOWN 08-18 18:49:10.384 4206 4206 D mUHDSTBGlobalkeyBroadCastReceiver: onReceive() keyCode : 84, action : KeyEvent.ACTION_UP Why both logs are different ? It may make some issue ? |
|
|
Hi Bcan Yeh, I reproduced the issue. So I attached it for you. |
|
|
Hi Mr. Yoon, In main_log_OK-2.log: ---------------------------------------------------------------------- 08-18 18:49:10.310 3316 3396 I WindowManager: [framework][WindowManager][Info] KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_SEARCH, scanCode=0, metaState=0, flags=0x0, repeatCount=0, eventTime=201877, downTime=201877, deviceId=-1, source=0x101 } 08-18 18:49:10.314 3316 3396 I WindowManager: [framework][WindowManager][Info] KeyEvent { action=ACTION_UP, keyCode=KEYCODE_SEARCH, scanCode=0, metaState=0, flags=0x0, repeatCount=0, eventTime=201877, downTime=201877, deviceId=-1, source=0x101 } 08-18 18:49:10.315 4206 4206 D mUHDSTBGlobalkeyBroadCastReceiver: onReceive() keyCode : 84, action : KeyEvent.ACTION_DOWN 08-18 18:49:10.316 4206 4206 D KeyEventManager: onKeyDown : 84 08-18 18:49:10.316 4206 4206 D KeyEventManager: onKeyDown : SEARCH 08-18 18:49:10.384 4206 4206 D mUHDSTBGlobalkeyBroadCastReceiver: onReceive() keyCode : 84, action : KeyEvent.ACTION_UP 08-18 18:49:10.384 4206 4206 D KeyEventManager: onKeyUp : 84, isLongKey : false 08-18 18:49:10.385 4206 4206 D KeyEventManager: onKeyUp : SEARCH ---------------------------------------------------------------------- In main_log_NOK-3.log: ---------------------------------------------------------------------- 08-19 12:20:47.723 3317 3395 I WindowManager: [framework][WindowManager][Info] KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_SEARCH, scanCode=0, metaState=0, flags=0x0, repeatCount=0, eventTime=201354, downTime=201354, deviceId=-1, source=0x101 } 08-19 12:20:47.725 3317 3395 I WindowManager: [framework][WindowManager][Info] KeyEvent { action=ACTION_UP, keyCode=KEYCODE_SEARCH, scanCode=0, metaState=0, flags=0x0, repeatCount=0, eventTime=201354, downTime=201354, deviceId=-1, source=0x101 } 08-19 12:20:47.726 4165 4165 D mUHDSTBGlobalkeyBroadCastReceiver: onReceive() keyCode : 84, action : KeyEvent.ACTION_UP 08-19 12:20:47.726 4165 4165 D KeyEventManager: onKeyUp : 84, isLongKey : false 08-19 12:20:47.726 4165 4165 D KeyEventManager: onKeyUp : SEARCH 08-19 12:20:47.733 4165 4165 D mUHDSTBGlobalkeyBroadCastReceiver: onReceive() keyCode : 84, action : KeyEvent.ACTION_UP 08-19 12:20:47.733 4165 4165 D KeyEventManager: onKeyUp : 84, isLongKey : false 08-19 12:20:47.733 4165 4165 D KeyEventManager: onKeyUp : SEARCH ---------------------------------------------------------------------- 1. The tag 'WindowManager' belongs to 'system_server'. It is a process of android framework. In both cases, it means that framework sends ACTION_DOWN and ACTION_UP. 2. The tag 'mUHDSTBGlobalkeyBroadCastReceiver' and 'KeyEventManager' belong to 'com.skb.tv'(SKB Launcher). In NOK case, mUHDSTBGlobalkeyBroadCastReceiver recognized 2 ACTION_UP instead of ACTION_DOWN/ACTION_UP 3. There might be some problem in 'com.skb.tv'. 4. Without modifying firmware, there are 2 possible methods to workaround. a. Change the key list of 'VOD' command. Maybe another key combination will not result in this problem. b. Reset ATT test and run it again. |
|
|
Hi Mr. Bcan Yeh, I sent your feedback to MW. Their answer is Search key is Global key. If ACTION_DOWN and ACTION_UP inputted without enough interval, then MW will send ACTION_UP to home_ui. So could you add more time for ACTION_UP ? |
|
|
Hi Mr.Yoon, What AttDaemon does in the step "VOD test" is just send a key code with one command "input keyevent xxx". I'm not sure is there any way to split a keyevent into a key_down event and a key_up event. I will survey for that. |
|
|
Hi Mr.Yoon, Could you provide the scanCode of KEYCODE_SEARCH(AndroidKeyCode 84) ? Thank you. |
|
|
Dear Mr. Bcan Yeh, KEYCODE_SEARCH is 125. I checked it with below command, then it worked. Could you test it ? sendevent /dev/input/event1 1 125 1; => ACTION_DOWN for Search sendevent /dev/input/event1 0 0 0; sendevent /dev/input/event1 1 125 0; => ACTION_UP for search sendevent /dev/input/event1 0 0 0; * /dev/input/event1 => input device 장치 번호, 125 => 입력하는 key의 linux scancode 값 그럼, 수고하세요 |
|
|
Dear Mr Bcan Yeh, If you revoke authentication, then it need to reset SKB system to use its authentication code again. So could you use below data for your test. It is authentication code for Factory test only. 717033 100601047065 Please be careful to use it. It should not use for factory only. So please use it for your test only. |
|
|
Hi Mr.Yoon, The method of using sendevent command need: 1. file permission ------------------------------------------------------- console:/data # ll /dev/input/event1 crw-rw---- 1 root input 13, 65 2015-01-01 09:00 /dev/input/event1 ------------------------------------------------------- AttDaemon has no permission to access this character file. 2. sepolicy ------------------------------------------------------- #============= system_app ============== allow system_app input_device:chr_file { ioctl open read write }; ------------------------------------------------------- Both need modification of framework. I have no idea about how to workaround for SEARCH_KEY problem. Maybe you can consider my suggestions before. |
|
|
Hi Mr. Bcan Yeh, I discussed with TV Storm about it. They said that This issue is a android issue. We already have it. They think that it should Add SEPOLICY allowance or Modify Android Framework And TV Storm said that they don't know how simulate key input. Do you think is there any solution for it ? |
|
|
Hi Mr.Yoon, The purpose of key code "1C" is to start the search page of the launcher. Maybe we can just start the search page directly while receiving "1C". Could you ask SKB to provide some information or code snippet for starting the search page ? |
|
|
Hi Bcan Yeh, We discussed with UI company. He guided to run Search window as follows : Intent intent = new Intent(Intent.ACTION_VIEW); intent.setData(Uri.parse("smartstb://foreground")); intent.putExtra("MAIN_ONNEWINTENT_SEARCH_NO_VOICE_SEARCH", true); startActivity(intent); Could you check it and update ? |
|
|
Hi Mr.Yoon, Please use AttDaemon version 200901 for this workaround. https://drive.google.com/file/d/1tLErMrysekQxrJXrHfAQx0he2Qy4OWaC/view?usp=sharing |
|
|
Hi Bcan Yeh, It tested HM Solution. And they inform that is OK. So I will close it. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-08-14 19:53 | (ALTech) SY Yoon | New Issue | |
| 2020-08-14 19:53 | (ALTech) SY Yoon | Status | new => assigned |
| 2020-08-14 19:53 | (ALTech) SY Yoon | Assigned To | => (SW) Bcan Yeh |
| 2020-08-14 19:53 | (ALTech) SY Yoon | File Added: main_log_OK.log | |
| 2020-08-14 19:53 | (ALTech) SY Yoon | File Added: main_log_NOK.log | |
| 2020-08-14 19:53 | (ALTech) SY Yoon | Issue Monitored: (ALTech) Jason Park | |
| 2020-08-14 19:54 | (ALTech) SY Yoon | Issue Monitored: (ALTech) Juyoung Park | |
| 2020-08-14 19:54 | (ALTech) SY Yoon | Issue Monitored: (ALTech) Wooshin Kang | |
| 2020-08-14 19:54 | (ALTech) SY Yoon | Issue Monitored: (SW) Kerwin Chen | |
| 2020-08-14 19:55 | (ALTech) SY Yoon | Issue Monitored: (SW) Jacky Chiang | |
| 2020-08-14 19:55 | (ALTech) SY Yoon | Note Added: 0004064 | |
| 2020-08-18 16:47 | (SW) Bcan Yeh | Note Added: 0004072 | |
| 2020-08-18 16:47 | (SW) Bcan Yeh | Assigned To | (SW) Bcan Yeh => (ALTech) SY Yoon |
| 2020-08-18 18:39 | (ALTech) SY Yoon | Assigned To | (ALTech) SY Yoon => (SW) Bcan Yeh |
| 2020-08-18 18:39 | (ALTech) SY Yoon | File Added: main_log_OK-2.log | |
| 2020-08-18 18:39 | (ALTech) SY Yoon | File Added: main_log_NOK-2.log | |
| 2020-08-18 18:39 | (ALTech) SY Yoon | Note Added: 0004074 | |
| 2020-08-18 20:03 | (SW) Bcan Yeh | Note Added: 0004076 | |
| 2020-08-18 20:03 | (SW) Bcan Yeh | Assigned To | (SW) Bcan Yeh => (ALTech) SY Yoon |
| 2020-08-19 11:15 | (ALTech) SY Yoon | Note Added: 0004082 | |
| 2020-08-19 11:34 | (ALTech) SY Yoon | File Added: main_log_NOK-3.log | |
| 2020-08-19 11:34 | (ALTech) SY Yoon | Note Added: 0004083 | |
| 2020-08-19 18:13 | (ALTech) SY Yoon | Assigned To | (ALTech) SY Yoon => (SW) Bcan Yeh |
| 2020-08-25 17:59 | (SW) Bcan Yeh | Note Added: 0004124 | |
| 2020-08-25 18:00 | (SW) Bcan Yeh | Assigned To | (SW) Bcan Yeh => (ALTech) SY Yoon |
| 2020-08-26 10:21 | (ALTech) SY Yoon | Note Added: 0004128 | |
| 2020-08-26 19:43 | (SW) Bcan Yeh | Note Added: 0004138 | |
| 2020-08-27 12:00 | (SW) Bcan Yeh | Note Added: 0004147 | |
| 2020-08-27 13:44 | (ALTech) SY Yoon | Note Added: 0004148 | |
| 2020-08-28 13:39 | (ALTech) SY Yoon | Note Added: 0004159 | |
| 2020-08-28 18:24 | (SW) Bcan Yeh | Note Added: 0004163 | |
| 2020-08-31 12:41 | (ALTech) SY Yoon | Note Added: 0004169 | |
| 2020-09-01 10:29 | (ALTech) SY Yoon | Assigned To | (ALTech) SY Yoon => (SW) Bcan Yeh |
| 2020-09-01 14:34 | (SW) Bcan Yeh | Note Added: 0004185 | |
| 2020-09-01 14:35 | (SW) Bcan Yeh | Assigned To | (SW) Bcan Yeh => (ALTech) SY Yoon |
| 2020-09-01 17:00 | (ALTech) SY Yoon | Assigned To | (ALTech) SY Yoon => (SW) Bcan Yeh |
| 2020-09-01 17:00 | (ALTech) SY Yoon | Note Added: 0004186 | |
| 2020-09-01 21:09 | (SW) Bcan Yeh | Note Added: 0004190 | |
| 2020-09-01 21:10 | (SW) Bcan Yeh | Assigned To | (SW) Bcan Yeh => (ALTech) SY Yoon |
| 2020-09-14 21:27 | (ALTech) SY Yoon | Note Added: 0004331 | |
| 2020-09-14 21:28 | (ALTech) SY Yoon | Status | assigned => closed |
| 2020-09-14 21:28 | (ALTech) SY Yoon | Resolution | open => fixed |
